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

feat(testskeleton.go): introduce UUID generation required by Azure Terratest implementation #3

Merged
merged 2 commits into from
Aug 21, 2023

Conversation

FoSix
Copy link
Contributor

@FoSix FoSix commented Jul 18, 2023

Description

Introduce UUID generation required by Azure Terratest implementation.

Motivation and Context

In Azure we relay on UUID as a source of random names for RGs, Storage Accounts and name prefixes. To retain the same logic we had in all pre-Terratest workflows this change is pushed.

How Has This Been Tested?

This code is already running on a PR branch for Azure repo introducing Terratest in general.

Types of changes

  • New feature (non-breaking change which adds functionality)

Checklist

  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes if appropriate.
  • All new and existing tests passed.

@welcome-to-palo-alto-networks

🎉 Thanks for opening this pull request! We really appreciate contributors like you! 🙌

@FoSix FoSix changed the title feat: introduce UUID generation required by Azure Terratest implementation feat(testskeleton.go): introduce UUID generation required by Azure Terratest implementation Jul 18, 2023
@FoSix FoSix merged commit 3993a9b into main Aug 21, 2023
@FoSix FoSix deleted the introduce-azure-modifications branch August 21, 2023 07:05
@welcome-to-palo-alto-networks

🎉 Congrats on getting your first pull request merged! We here at Palo Alto Networks are so grateful! ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants