-
Notifications
You must be signed in to change notification settings - Fork 3
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
VLTCLT-51 Add client method to get or create encryption key id #447
Conversation
Hello nicolas2bert,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
ping |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command:
Alternatively, the |
Action: 'GetOrCreateEncryptionKeyId', | ||
canonicalId, | ||
}; | ||
this.request('POST', '/', false, (err, data, code) => { |
There was a problem hiding this comment.
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? 🤔
There was a problem hiding this comment.
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,
};
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
57cd75a
to
01a4614
Compare
01a4614
to
da3f8db
Compare
/create_integration_branches |
ConflictA conflict has been raised during the creation of 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 |
@bert-e approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: approve, create_integration_branches |
da3f8db
to
855eacf
Compare
History mismatchMerge commit #da3f8db2c20f35eacc6961b29ae64ea07470ac01 on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: approve, create_integration_branches |
@bert-e reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: approve, create_integration_branches |
ConflictA conflict has been raised during the creation of 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 |
ping |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: approve, create_integration_branches |
855eacf
to
e8e5b1c
Compare
History mismatchMerge commit #855eacf2781557ffcaeef7543434873ce066fb3a on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: approve, create_integration_branches |
@bert-e reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: approve, create_integration_branches |
ConflictA conflict has been raised during the creation of 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 |
e8e5b1c
to
a4b098e
Compare
ping |
@bert-e reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: approve, create_integration_branches |
ConflictA conflict has been raised during the creation of 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 |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: approve, create_integration_branches |
ConflictA conflict has been raised during the update of Please resolve the conflict on the integration branch ( 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 |
ConflictA conflict has been raised during the update of Please resolve the conflict on the integration branch ( 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 |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue VLTCLT-51. Goodbye nicolas2bert. The following options are set: approve, create_integration_branches |
No description provided.