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

[WFLY-17183] Fix the description of the filesystem-realm update-key-p… #16264

Merged
merged 1 commit into from Nov 14, 2022

Conversation

anilabhabaral
Copy link
Contributor

@anilabhabaral anilabhabaral commented Nov 7, 2022

@github-actions github-actions bot added the deps-ok Dependencies have been checked, and there are no significant changes label Nov 7, 2022
@anilabhabaral
Copy link
Contributor Author

Hi @bstansberry @fjuma could you please review this PR ?

Copy link
Contributor

@fjuma fjuma left a comment

Choose a reason for hiding this comment

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

Thanks for working on this @anilabhabaral! Just have some small comments.

[source, options="nowrap"]
----
/subsystem=elytron/filesystem-realm=fsRealm:update-key-pair(key-store=newKeyStore, key-store-alias=newKeyStoreAlias)
/subsystem=elytron/filesystem-realm=keystore:write-attribute(name=key-store, value=newKeystore)
Copy link
Contributor

Choose a reason for hiding this comment

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

Just to be consistent with the name of the filesystem-realm used in the other examples, we should use filesystem-realm=fsRealm here instead of filesystem-realm=keystore.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

[source, options="nowrap"]
----
/subsystem=elytron/filesystem-realm=fsRealm:update-key-pair(key-store=newKeyStore, key-store-alias=newKeyStoreAlias)
/subsystem=elytron/filesystem-realm=keystore:write-attribute(name=key-store, value=newKeystore)
/subsystem=elytron/filesystem-realm=keystore:write-attribute(name=key-store-alias, value=newKeystoreAlias)
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here, filesystem-realm=fsRealm.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

Copy link
Contributor

@fjuma fjuma left a comment

Choose a reason for hiding this comment

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

Thanks for the updates @anilabhabaral, looks good! Please squash the commits and then this should be good to go.

@anilabhabaral
Copy link
Contributor Author

anilabhabaral commented Nov 9, 2022

Hi @fjuma I am facing some issue while squashing the commits in my local repo.

I think repository's manager can squash all the commits in a pull request into a single commit by selecting "Squash and merge" on a pull request.It will be helpful if you could do this for me.

@cam-rod
Copy link
Contributor

cam-rod commented Nov 9, 2022

Hey @anilabhabaral, it looks the main branch was merged into yours, instead of the other way around. You'll need to delete the merge commit, and use an interactive rebase to squash the existing commits into a single one:

  • Checkout to your branch, and run git reset HEAD~1 --hard, which will delete the merge commit. The "hard" option also deletes the changes that were staged by the reset, so this will give you a clean slate.
  • Now checkout the main branch, and run git pull to get the latest changes, before switching back to your branch.
  • Run git rebase -i main to start the interactive rebase onto the main branch. This will open a file to modify the commits in (you can set the editor with git config --global core.editor <editor_command>)
    • The screen that appears will explain how to properly modify the commits. The oldest commit is at the top, so replace pick in the second commit and down with fixup to squash all the commits into the first one, and discard the message.
    • Save the file and close it, the rebase will execute.
  • Once the squash and rebase is complete, run git push -f to push the rewritten branch history.

A quick summary of commands:

git checkout WFLY-17183
git reset HEAD~1 --hard

git checkout main
git pull
git checkout WFLY-17183

git rebase -i main

# replace `pick` with `fixup` in all but the first commit, save and exit the file

git push -f

Let me know if you have any questions.

Copy link
Contributor

@fjuma fjuma left a comment

Choose a reason for hiding this comment

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

Thanks very much @cam-rod for helping and thanks @anilabhabaral for the update! Looks good now.

@cam-rod
Copy link
Contributor

cam-rod commented Nov 9, 2022

Looks good @anilabhabaral, thanks!

@anilabhabaral
Copy link
Contributor Author

Thanks @cam-rod , @fjuma for your help!

@anilabhabaral
Copy link
Contributor Author

Hello @bstansberry could you please check whether this PR is ready for merge ?

@bstansberry
Copy link
Contributor

@anilabhabaral Can you use 'git commit --amend' and fix the commit message, i.e. just the WFLY-17183 line? The current first line is what people reading history see and it's not useful info. Thanks.

Please ping @fjuma when ready; she is a WildFly merger and can merge it.

@anilabhabaral
Copy link
Contributor Author

Thank you @bstansberry . I modified the commit message.

Hello @fjuma could you please check whether this PR is ready for merge ?

@fjuma fjuma merged commit 02c734a into wildfly:main Nov 14, 2022
@anilabhabaral
Copy link
Contributor Author

Thanks @fjuma

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deps-ok Dependencies have been checked, and there are no significant changes
Projects
None yet
4 participants