Code Monkey home page Code Monkey logo

pulumi-vultr's Issues

vultr.DnsRecord - MX and CNAME records

Hi,

when I created a new domain via "vultr.DnsRecord", it automatically adds a MX and a CNAME record. Why? How can I delete them?

import pulumi
import ediri_vultr as vultr

my_domain = vultr.DnsDomain("foobar", domain="foobar.foo", ip="1.2.3.4")
A     1.2.3.4         300
CNAME * foobar.foo    300
MX    foobar.foo      300 10
NS    ns1.vultr.com   300
NS    ns2.vultr.com   300

Thanks

Broken link to docs

The docs link in README.md seems to be broken:

For detailed reference documentation, please visit [the Pulumi registry](https://www.pulumi.com/registry/packages/pulumi-vultr/api-docs/).

This isn't a huge dealbreaker for me, as going through the source code is simple enough. However, it'd probably make life easier to have this module re-uploaded to the registry and have the docs rendered. ๐Ÿ˜„

P.S. Thanks for this awesome module, it's very useful to me!

In-place upgrade attempted on incompatible server type

Vultr docs specify that in-place upgrades are not supported when changing server types. However if you change an instance type using the Python interface from a vc2 type plan to a vhp type plan, Pulumi attempts to modify the server type in-place, resulting in an error from Vultr:

"{\"error\":\"Unable to upgrade plan: This plan is not an upgrade.\",\"status\":500}"

To reproduce: create a Pulumi configuration with an plan ID of vc2-1c-1gb, deploy, change plan ID to vhp-1c-1gb-amd, attempt redeploy.

I have only tested the specific scenario described above, and only using the Pulumi Python interface.

After upgrading from 2.19.0 to 2.21.0, pulumi preview(or up) throws error

Diagnostics:
  pulumi:providers:vultr (default_2_21_0_github_/api.github.com/dirien/pulumi-vultr):
    error: could not read plugin [$HOME/.pulumi/plugins/resource-vultr-v2.21.0/pulumi-resource-vultr] stdout: EOF

  pulumi:pulumi:Stack ($MY_STACK):
    error: fatal: failed to Init GRPC to register RPC handlers: failed to create resource provider: info.P must be constructed with ShimProvider or ShimProviderWithContext: found non-conforming type *muxer.ProviderShim

Downgrading from 2.21.0 to 2.19.0 fixed the issue.

Is there anything that I could be a help to fix the issue?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.