Skip to content

deployment release counter exposed in post stage #2555

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

Merged
merged 1 commit into from
Nov 2, 2022

Conversation

kripanshdevtron
Copy link
Contributor

@kripanshdevtron kripanshdevtron commented Oct 31, 2022

Description

deployment release counter needed in env vars.

Fixes #2569

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have tested it for all user roles
  • I have added all the required unit/api test cases

@kripanshdevtron kripanshdevtron self-assigned this Nov 2, 2022
@kripanshdevtron kripanshdevtron added the enhancement New feature or request label Nov 2, 2022
@kripanshdevtron kripanshdevtron merged commit 130f363 into main Nov 2, 2022
@kripanshdevtron kripanshdevtron deleted the release-id-env-param branch November 2, 2022 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature: Need a unique value in post-deployment stage for every new deployment
2 participants