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

VLTCLT-51 Add client method to get or create encryption key id #447

Merged

Conversation

nicolas2bert
Copy link
Contributor

No description provided.

@bert-e
Copy link
Contributor

bert-e commented Sep 26, 2024

Hello nicolas2bert,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Sep 26, 2024

Incorrect fix version

The Fix Version/s in issue VLTCLT-51 contains:

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 7.10.15

  • 8.2.10

  • 8.3.21

  • 8.4.1

  • 8.5.1

Please check the Fix Version/s of VLTCLT-51, or the target
branch of this pull request.

@nicolas2bert
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Sep 30, 2024

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

Action: 'GetOrCreateEncryptionKeyId',
canonicalId,
};
this.request('POST', '/', false, (err, data, code) => {

Choose a reason for hiding this comment

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

Is a POST to / doing what we want to do here? 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, :) It uses an RPC (remote procedure call) protocol. All actions are sent to a single endpoint '/' and the payload specifies the action to do:

const data = {
      Action: 'GetOrCreateEncryptionKeyId',
      canonicalId,
  };

Choose a reason for hiding this comment

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

Ooh I see. I'm not familiar with the vault API and I assumed it uses HTTP routes.

Copy link
Contributor

Choose a reason for hiding this comment

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

This action doesn't exist for now I think

@nicolas2bert nicolas2bert force-pushed the improvement/VLTCLT-51/getOrCreateEncryptionKeyId branch from 57cd75a to 01a4614 Compare September 30, 2024 13:26
lib/IAMClient.js Outdated Show resolved Hide resolved
@nicolas2bert nicolas2bert force-pushed the improvement/VLTCLT-51/getOrCreateEncryptionKeyId branch from 01a4614 to da3f8db Compare October 1, 2024 16:01
@nicolas2bert
Copy link
Contributor Author

/create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Conflict

A conflict has been raised during the creation of
integration branch w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId with contents from improvement/VLTCLT-51/getOrCreateEncryptionKeyId
and development/8.2.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId origin/development/8.2
 $ git merge origin/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId

The following options are set: create_integration_branches

@nicolas2bert
Copy link
Contributor Author

@bert-e approve

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/6.4
  • development/7.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Build failed

The build for commit did not succeed in branch w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId.

The following options are set: approve, create_integration_branches

@nicolas2bert nicolas2bert force-pushed the improvement/VLTCLT-51/getOrCreateEncryptionKeyId branch from da3f8db to 855eacf Compare October 1, 2024 16:09
@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

History mismatch

Merge commit #da3f8db2c20f35eacc6961b29ae64ea07470ac01 on the integration branch
w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId is merging a branch which is neither the current
branch improvement/VLTCLT-51/getOrCreateEncryptionKeyId nor the development branch
development/8.2.

It is likely due to a rebase of the branch improvement/VLTCLT-51/getOrCreateEncryptionKeyId and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

The following options are set: approve, create_integration_branches

@nicolas2bert
Copy link
Contributor Author

@bert-e reset

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Reset complete

I have successfully deleted this pull request's integration branches.

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Conflict

A conflict has been raised during the creation of
integration branch w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId with contents from improvement/VLTCLT-51/getOrCreateEncryptionKeyId
and development/8.2.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId origin/development/8.2
 $ git merge origin/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId

The following options are set: approve, create_integration_branches

@nicolas2bert
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/6.4
  • development/7.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Build failed

The build for commit did not succeed in branch w/8.5/improvement/VLTCLT-51/getOrCreateEncryptionKeyId.

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Build failed

The build for commit did not succeed in branch w/8.3/improvement/VLTCLT-51/getOrCreateEncryptionKeyId.

The following options are set: approve, create_integration_branches

@nicolas2bert nicolas2bert force-pushed the improvement/VLTCLT-51/getOrCreateEncryptionKeyId branch from 855eacf to e8e5b1c Compare October 1, 2024 16:18
@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

History mismatch

Merge commit #855eacf2781557ffcaeef7543434873ce066fb3a on the integration branch
w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId is merging a branch which is neither the current
branch improvement/VLTCLT-51/getOrCreateEncryptionKeyId nor the development branch
development/8.2.

It is likely due to a rebase of the branch improvement/VLTCLT-51/getOrCreateEncryptionKeyId and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

The following options are set: approve, create_integration_branches

@nicolas2bert
Copy link
Contributor Author

@bert-e reset

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Reset complete

I have successfully deleted this pull request's integration branches.

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Conflict

A conflict has been raised during the creation of
integration branch w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId with contents from improvement/VLTCLT-51/getOrCreateEncryptionKeyId
and development/8.2.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId origin/development/8.2
 $ git merge origin/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId

The following options are set: approve, create_integration_branches

@nicolas2bert nicolas2bert force-pushed the improvement/VLTCLT-51/getOrCreateEncryptionKeyId branch from e8e5b1c to a4b098e Compare October 1, 2024 16:20
@nicolas2bert
Copy link
Contributor Author

ping

@nicolas2bert
Copy link
Contributor Author

@bert-e reset

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Reset complete

I have successfully deleted this pull request's integration branches.

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Conflict

A conflict has been raised during the creation of
integration branch w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId with contents from improvement/VLTCLT-51/getOrCreateEncryptionKeyId
and development/8.2.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId origin/development/8.2
 $ git merge origin/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.2/improvement/VLTCLT-51/getOrCreateEncryptionKeyId

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/6.4
  • development/7.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Build failed

The build for commit did not succeed in branch w/8.5/improvement/VLTCLT-51/getOrCreateEncryptionKeyId.

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Build failed

The build for commit did not succeed in branch w/8.3/improvement/VLTCLT-51/getOrCreateEncryptionKeyId.

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Conflict

A conflict has been raised during the update of
integration branch w/8.4/improvement/VLTCLT-51/getOrCreateEncryptionKeyId with contents from w/8.3/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
and development/8.4.

Please resolve the conflict on the integration branch (w/8.4/improvement/VLTCLT-51/getOrCreateEncryptionKeyId).

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout w/8.4/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
 $ git pull  # or "git reset --hard origin/w/8.4/improvement/VLTCLT-51/getOrCreateEncryptionKeyId"
 $ git merge origin/development/8.4
 $ # <intense conflict resolution>
 $ git commit
 $ git merge origin/w/8.3/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.4/improvement/VLTCLT-51/getOrCreateEncryptionKeyId

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Conflict

A conflict has been raised during the update of
integration branch w/8.5/improvement/VLTCLT-51/getOrCreateEncryptionKeyId with contents from w/8.4/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
and development/8.5.

Please resolve the conflict on the integration branch (w/8.5/improvement/VLTCLT-51/getOrCreateEncryptionKeyId).

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout w/8.5/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
 $ git pull  # or "git reset --hard origin/w/8.5/improvement/VLTCLT-51/getOrCreateEncryptionKeyId"
 $ git merge origin/development/8.5
 $ # <intense conflict resolution>
 $ git commit
 $ git merge origin/w/8.4/improvement/VLTCLT-51/getOrCreateEncryptionKeyId
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.5/improvement/VLTCLT-51/getOrCreateEncryptionKeyId

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Build failed

The build for commit did not succeed in branch w/8.5/improvement/VLTCLT-51/getOrCreateEncryptionKeyId.

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

Build failed

The build for commit did not succeed in branch w/8.5/improvement/VLTCLT-51/getOrCreateEncryptionKeyId.

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Oct 1, 2024

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/7.10

  • ✔️ development/8.2

  • ✔️ development/8.3

  • ✔️ development/8.4

  • ✔️ development/8.5

The following branches have NOT changed:

  • development/6.4
  • development/7.4

Please check the status of the associated issue VLTCLT-51.

Goodbye nicolas2bert.

The following options are set: approve, create_integration_branches

@bert-e bert-e merged commit a4b098e into development/7.10 Oct 1, 2024
1 check passed
@bert-e bert-e deleted the improvement/VLTCLT-51/getOrCreateEncryptionKeyId branch October 1, 2024 17:17
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