Updated code that validates managed_image_os_disk_snapshot_name and managed_image_data_disk_snapshot_prefix#511
Conversation
…anaged_image_data_disk_snapshot_prefix MyImage2025.01.01-snapshot is a perfectly valid snapshot name, but original code does not accept it.
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Vladimir Khvostov seems not to be a GitHub user. Have you signed the CLA already but the status is still pending? Recheck it. |
1 similar comment
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Vladimir Khvostov seems not to be a GitHub user. Have you signed the CLA already but the status is still pending? Recheck it. |
|
Hey @VladimirKhvostov this change seems good to me, thank you for the unit test changes as well. Can you please sign the CLA mentioned in the previous comment? Once that's done I will validate it quickly and then we should be good to merge this |
|
@VladimirKhvostov Could you please sign the CLA so we can proceed with the PR? |
Description
MyImage2025.01.01-snapshot is a perfectly valid snapshot name, but original code does not accept it. Original code does not allow to use dots in the snapshot name.
Rollback Plan
Changes to Security Controls
No