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.

Sign up for GitHub

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

Jump to bottom

V1.3.3 preview #331

Merged
merged 31 commits into from
Jun 12, 2023
Merged

V1.3.3 preview #331

merged 31 commits into from
Jun 12, 2023

Conversation

kevinhillinger
Copy link
Member

No description provided.

@kevinhillinger
initial laydown of distinct operations for stages
6d50dc0
@kevinhillinger
commenting out stage notification service registration
5cb2062
@kevinhillinger
removing event grid registration and implementing a stage deployment …
05ddc0c 
…poller
@kevinhillinger
changes:
1ba55a5 
- adding unknown status to SDK
- created stage deployment poller and wired up
- regenerated api code
@kevinhillinger
mod
9e5e8e7
@kevinhillinger
setting values for stage deploy operation
6ff941b
@kevinhillinger
after upgrading to latest az go sdk, fixing client name convention
461c0ff
@kevinhillinger
changes:
8cc6db6 
- azure deployment name finder by operation id (azure deployment name for nested templates can be calculated values so have to find it AFTER)
- poller update to accept azure deployment name
@kevinhillinger
laundry list:
705cc28 
- fixing operation service instance to operation as 1-1
- ensuring that we're processing more than 1 message at a time (that it's async)
- adding in the operation deployStage as supported in the operator
- renaming OperationService to OperationManager
- logging finder results as a trace
- defaulting the max messages to 10
- setting value
@kevinhillinger
updating comment
d633766
@kevinhillinger
updating field name
310d5af
@kevinhillinger
checking for status failure in order to return and error if the stage…
25a768f 
… deployment failed.
@kevinhillinger
adding missing message data for deploy stage
e4b3952
@kevinhillinger
making stage operation create async
361f3c4
@kevinhillinger
cleanup
5e224df
@kevinhillinger
rename file
13a3246
@kevinhillinger
adding azure deployment name to the attributes of the operation
c2b27a3
@kevinhillinger
retry stage now pulling from attrs of operation
20c7d2e
@kevinhillinger
removing setting operation id as the parent for all templates
d7622bb
@kevinhillinger
fixing name
de27e18
@kevinhillinger
removing old test files commented out
cac5f6f
@kevinhillinger
nested template name parameter
a504113
@kevinhillinger
adding change to look at operation id
33038c1
@kevinhillinger
azure nested template name set to parameter value
193b6e4
@kevinhillinger
adding error to finder
cb65e43
@kevinhillinger
fixing template ids
ad3c1bc
@kevinhillinger
status none not unknown
4991b84
@kevinhillinger
making stage have a composite primary key
46e2f99
@kevinhillinger
v1.3.3-preview
2c44c8c
@kevinhillinger
adding tests
df6fda5
@kevinhillinger kevinhillinger self-assigned this Jun 12, 2023
This was linked to issues Jun 12, 2023
Stage messages not received as desired v1.3.2 #330
Closed
Bug: stageRetried event message type not in the correct status #326
Closed
Bug: stage retries not honoring max retries value #325
Closed
@bobjac bobjac merged commit c7f4be2 into v1 Jun 12, 2023
1 check passed
@bobjac bobjac deleted the v1.3.3-preview branch June 12, 2023 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bobjac bobjac bobjac approved these changes

Assignees

@kevinhillinger kevinhillinger

Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@kevinhillinger @bobjac