Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow - in disk snapshot names #1574

Merged
merged 1 commit into from
Jul 15, 2018
Merged

Conversation

CoRfr
Copy link
Contributor

@CoRfr CoRfr commented Jul 14, 2018

It appears that - was omitted from the possible character in snapshot
names.

It doesn't seem like there is any issue when using - in the name, as
I was able to create snapshots with dashes both from the portal and
through this plugin (with this patch applied).

It appears that - was omitted from the possible character in snapshot
names.
It doesn't seem like there is any issue when using - in the name, as
I was able to create snapshots with dashes both from the portal and
through this plugin (with this patch applied).
@CoRfr
Copy link
Contributor Author

CoRfr commented Jul 15, 2018

Oh I see where the format is coming from:

https://docs.microsoft.com/en-us/rest/api/compute/snapshots/update

The name of the snapshot that is being created. The name can't be changed after the snapshot is created. Supported characters for the name are a-z, A-Z, 0-9 and _. The max name length is 80 characters.

In practice though, it appears that '-' is supported. I'm not sure how to request REST API updates.

@CoRfr
Copy link
Contributor Author

CoRfr commented Jul 15, 2018

Also it seems that disks have the same requirements for names, which is not enforced in terraform:
https://docs.microsoft.com/en-us/rest/api/compute/disks/createorupdate

The documentation is also outdated since - are clearly accepted for disk names as well.

Copy link
Contributor

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - thanks for this 👍

@tombuildsstuff tombuildsstuff added this to the 1.10.0 milestone Jul 15, 2018
@tombuildsstuff tombuildsstuff merged commit f3eaec9 into hashicorp:master Jul 15, 2018
tombuildsstuff added a commit that referenced this pull request Jul 15, 2018
@tombuildsstuff
Copy link
Contributor

hi @CoRfr

Just to let you know that is now available in [v1.10 of the AzureRM Provider(https://github.com/terraform-providers/terraform-provider-azurerm/blob/v1.10.0/CHANGELOG.md#1100-july-21-2018) - which you can update to this version by specifying it in the Provider block, like so:

provider "azurerm" {
  version = "=1.10.0"
}

Thanks!

@ghost
Copy link

ghost commented Mar 30, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants