search

Azure / deployment-environments

Sample infrastructure-as-code templates to get started with Azure Deployment Environments service.
MIT License
67 stars 210 forks source link

Not getting option to create Deployment environments on devportal #35

Closed ujjwalbarman closed 7 months ago

ujjwalbarman commented 7 months ago

Hi, I have been using Deployment environments for various demos but suddenly the option to create new environments disappeared from my dev portal. I can still access the environments created in the past but no option to create anything new. Checked all the setting and everything seems to be fine. I can still create devboxes from the portal but no environments. What can be the issue?

ericaguthan commented 7 months ago

Hi @ujjwalbarman

Can you elaborate on your current permissions and settings? If any of the components required to create an environment are missing, this button may be removed. Some things I recommend checking:

ericaguthan commented 7 months ago

Hi @ujjwalbarman It appears the screenshots are not attached. Additionally, it looks like your email signature has attached your phone number to this issue. You should be able to edit your previous message to remove it if you'd like.

ujjwalbarman commented 7 months ago

Hello Erica, Removed the messaged and resolved the issue. It was related to PAT. Even though there was a PAT which wasn't expired the thing didnt work. I regenerated a new PAT, created new secret and used the identifier which resolved the issue. Happy that it resolved but no idea why it happened earlier. The existing PAT wasn't expired so should have worked.

ujjwalbarman commented 7 months ago

resolved the issue. It was related to PAT. Even though there was a PAT which wasn't expired the thing didnt work. I regenerated a new PAT, created new secret and used the identifier which resolved the issue. Happy that it resolved but no idea why it happened earlier. The existing PAT wasn't expired so should have worked.

ericaguthan commented 7 months ago

@ujjwalbarman Glad to hear it is resolved! Do you have the version string at the end of the secret identifier when you add it to the catalog? That part of the identifier is not required for the catalog to sync and we have seen that cause similar confusion in the past. If the PAT secret has been updated in the Key Vault directly but a specific old version of the secret is referenced in the catalog, we will attempt to use the old PAT to sync. Removing the version string from the end of the secret ID will ensure the catalog always syncs based on the latest version of the secret.

ujjwalbarman commented 7 months ago

That's a very clear advice. Worth including in the ms learn documentation.

On Thu, Dec 7, 2023 at 5:47 PM Erica Guthan @.***> wrote:

@ujjwalbarman https://github.com/ujjwalbarman Glad to hear it is resolved! Do you have the version string at the end of the secret identifier when you add it to the catalog? That part of the identifier is not required for the catalog to sync and we have seen that cause similar confusion in the past. If the PAT secret has been updated in the Key Vault directly but a specific old version of the secret is referenced in the catalog, we will attempt to use the old PAT to sync. Removing the version string from the end of the secret ID will ensure the catalog always syncs based on the latest version of the secret.

— Reply to this email directly, view it on GitHub https://github.com/Azure/deployment-environments/issues/35#issuecomment-1845822470, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALDBHES6BHVSNQW4TJ4O35DYIH6KFAVCNFSM6AAAAABAHNXG56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVHAZDENBXGA . You are receiving this because you were mentioned.Message ID: @.***>

-- Thanks & Regards, Ujjwal Barman Mobile: +44(0)7574136579