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

Upped aliases API version to non-preview #198

Merged
merged 13 commits into from
Apr 2, 2022
Merged

Conversation

johnlokerse
Copy link
Contributor

@johnlokerse johnlokerse commented Mar 30, 2022

Checked if the current properties are still valid. With the newer version Microsoft.Subscription/aliases there are more properties present, tags for example.
Link to msdocs: https://docs.microsoft.com/en-us/azure/templates/microsoft.subscription/2021-10-01/aliases?tabs=bicep

As part of this Pull Request I have

  • Checked for duplicate Pull Requests
  • Associated it with relevant ADO items
  • Ensured my code/branch is up-to-date with the latest changes in the main branch
  • Performed testing and provided evidence.
  • Updated relevant and associated documentation.

Checked if the current properties are still valid. With the newer version `Microsoft.Subscription/aliases` there are more properties present, tags for example.
Link to msdocs: https://docs.microsoft.com/en-us/azure/templates/microsoft.subscription/2021-10-01/aliases?tabs=bicep
@ghost ghost added the Needs: Triage 🔍 Needs triaging by the team label Mar 30, 2022
@jtracey93
Copy link
Collaborator

Hey @johnlokerse,

Thanks for this, do you also want to add the additional properties as input parameters for this? I think they would be useful and has been on my mind to do 👍

Let me know

Thanks

Jack

@jtracey93 jtracey93 added enhancement and removed Needs: Triage 🔍 Needs triaging by the team labels Mar 30, 2022
@jtracey93 jtracey93 self-assigned this Mar 30, 2022
@johnlokerse
Copy link
Contributor Author

Sure I will try to update it tonight 👍

@johnlokerse
Copy link
Contributor Author

@jtracey93 I added the properties tags, managementGroupId, subscriptionTenantId and subscriptionOwnerId. The latter is unclear to me. I couldn't find it in the Azure Portal either. Is it the account admin under Subscription > Properties?

Copy link
Collaborator

@jtracey93 jtracey93 left a comment

Choose a reason for hiding this comment

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

Thanks for your work here @johnlokerse a few changes please 👍

Added input examples, added parTenantId, added author name, updated description of subscriptionOwnerId
@ghost ghost removed the Needs: Author Feedback label Mar 30, 2022
@johnlokerse
Copy link
Contributor Author

@jtracey93 Implemented your feedback! :-)

@johnlokerse johnlokerse requested a review from jtracey93 March 30, 2022 17:06
Copy link
Collaborator

@jtracey93 jtracey93 left a comment

Choose a reason for hiding this comment

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

Hey @johnlokerse,

Thanks for making those changes. A few more from this pass/review.

Could you also provide some testing evidence/screenshots? (if not possible let me know and we can do some testing for you)

Thanks

Jack 👍

@johnlokerse
Copy link
Contributor Author

I can provide a screenshot that shows the created subscription with the default tagging. So the changes work! The subscriptionOwner is set as myself, so that answers my question about what "subscriptionOwner" means. It's just a RBAC permission.
image

@ghost ghost removed the Needs: Author Feedback label Mar 31, 2022
@johnlokerse
Copy link
Contributor Author

@jtracey93 If I can find time I will take a look at the proposed changes later. 😃

@johnlokerse
Copy link
Contributor Author

Something like this @jtracey93? Made parManagementGroupId and parSubscriptionOwnerId optional using an empty string + empty() check. Tested while creating a new subscription. It works.

@johnlokerse johnlokerse requested a review from jtracey93 March 31, 2022 13:36
@jtracey93
Copy link
Collaborator

Something like this @jtracey93 Jack Tracey FTE? Made parManagementGroupId and parSubscriptionOwnerId optional using an empty string + empty() check. Tested while creating a new subscription. It works.

looking good. have you tested with them not empty also?

@johnlokerse
Copy link
Contributor Author

Something like this @jtracey93 Jack Tracey FTE? Made parManagementGroupId and parSubscriptionOwnerId optional using an empty string + empty() check. Tested while creating a new subscription. It works.

looking good. have you tested with them not empty also?

Yes. Tested with:

  • Empty (both)
  • Empty (one empty, one defined)
  • Both defined

Copy link
Collaborator

@jtracey93 jtracey93 left a comment

Choose a reason for hiding this comment

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

Last 2 pieces and we are there 👍👍👍

@ghost ghost removed the Needs: Author Feedback label Mar 31, 2022
@johnlokerse johnlokerse requested a review from jtracey93 March 31, 2022 14:10
Copy link
Contributor Author

@johnlokerse johnlokerse left a comment

Choose a reason for hiding this comment

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

Implemented feedback

Edit: @jtracey93 I see a requested change, but I cannot find it...

@jtracey93
Copy link
Collaborator

Implemented feedback

Edit: @jtracey93 Jack Tracey FTE I see a requested change, but I cannot find it...

No worries i will review today

@jtracey93
Copy link
Collaborator

@johnlokerse can you merge this PR to your forks branch johnlokerse#1

jtracey93
jtracey93 previously approved these changes Apr 1, 2022
@johnlokerse
Copy link
Contributor Author

@jtracey93 There was an error regarding the markdownlinter. Fixed it and the actions are now good.

@jtracey93 jtracey93 merged commit da35a05 into Azure:main Apr 2, 2022
@johnlokerse johnlokerse deleted the patch-3 branch April 2, 2022 13:59
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.

2 participants