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

⚠️ CONFLICT! Lineage pull request for: skeleton #65

Merged
merged 28 commits into from
May 31, 2023

Conversation

cisagovbot
Copy link

@cisagovbot cisagovbot commented May 22, 2023

Lineage Pull Request: CONFLICT

Lineage has created this pull request to incorporate new changes found in an
upstream repository:

Upstream repository: https://github.com/cisagov/skeleton-packer.git
Remote branch: HEAD

Check the changes in this pull request to ensure they won't cause issues with
your project.

The lineage/skeleton branch has one or more unresolved merge conflicts
that you must resolve before merging this pull request!

How to resolve the conflicts

  1. Take ownership of this pull request by removing any other assignees.

  2. Clone the repository locally, and reapply the merge:

    git clone git@github.com:cisagov/nessus-packer.git nessus-packer
    cd nessus-packer
    git remote add skeleton https://github.com/cisagov/skeleton-packer.git
    git remote set-url --push skeleton no_push
    git switch develop
    git checkout -b lineage/skeleton --track origin/develop
    git pull skeleton HEAD
    git status
  3. Review the changes displayed by the status command. Fix any conflicts and
    possibly incorrect auto-merges.

  4. After resolving each of the conflicts, add your changes to the
    branch, commit, and push your changes:

    git add .github/CODEOWNERS .github/dependabot.yml src/aws.yml src/example.yml src/requirements.yml 
    git commit
    git push --force --set-upstream origin lineage/skeleton

    Note that you may append to the default merge commit message
    that git creates for you, but please do not delete the existing
    content
    . It provides useful information about the merge that is
    being performed.

  5. Wait for all the automated tests to pass.

  6. Confirm each item in the "Pre-approval checklist" below.

  7. Remove any of the checklist items that do not apply.

  8. Ensure every remaining checkbox has been checked.

  9. Mark this draft pull request "Ready for review".

✅ Pre-approval checklist

Remove any of the following that do not apply. If you're unsure about
any of these, don't hesitate to ask. We're here to help!

  • ✌️ The conflicts in this pull request have been resolved.
  • All relevant type-of-change labels have been added.
  • All new and existing tests pass.

✅ Pre-merge checklist

Remove any of the following that do not apply. These boxes should
remain unchecked until the pull request has been approved.

  • Bump major, minor, patch, or pre-release version as
    appropriate

    via the bump_version.sh script if this repository is
    versioned and the changes in this PR warrant a version
    bump
    .
  • Finalize version.

✅ Post-merge checklist

Remove any of the following that do not apply.

  • Create a release.

Note
You are seeing this because one of this repository's maintainers has
configured Lineage to open pull requests.

For more information:

🛠 Lineage configurations for this project are stored in .github/lineage.yml

📚 Read more about Lineage

jsf9k and others added 20 commits February 27, 2023 10:54
Co-authored-by: Nicholas McDonnell <50747025+mcdonnnj@users.noreply.github.com>
If pip is installed first, then the OS _could_ pull different Python
packages than what would be installed via the
cisagov/ansible-role-python role; hence, the new ordering is more
controlled.

Co-authored-by: Nicholas McDonnell <50747025+mcdonnnj@users.noreply.github.com>
Co-authored-by: dav3r <david.redmin@trio.dhs.gov>
Add comments attributing two ignore directives with this repository.
Add a new, commented out ignore directive for github-actions for a
dependency that should be managed in this repository.
This is the latest minor release of Python so it makes sense to use it
as the default for this job.
…n_for_lint_job

Use Python 3.11 for the `lint` job in the `build` workflow
This is done automatically with the `pre-commit autoupdate` command.
However the `ansible-lint` hook is manually kept back as we have not
tested functionality to confirm that our roles will generally pass
with the new version.
Bumps [actions/setup-go](https://github.com/actions/setup-go) from 3 to 4.
- [Release notes](https://github.com/actions/setup-go/releases)
- [Commits](actions/setup-go@v3...v4)

---
updated-dependencies:
- dependency-name: actions/setup-go
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
…s/setup-go-4

Bump actions/setup-go from 3 to 4
When wheel gets installed alongside other packages, it may not get
used when those other packages are installed.  When that happens I see
warnings like this:
  DEPRECATION: ansible-core is being installed using the legacy
  'setup.py install' method, because it does not have a
  'pyproject.toml' and the 'wheel' package is not installed. pip 23.1
  will enforce this behaviour change. A possible replacement is to
  enable the '--use-pep517' option. Discussion can be found at
  pypa/pip#8559

This change should get rid of these warnings.

Nota bene: This is the practice we follow in the Dockerfile in
cisagov/skeleton-docker, but for some reason we never started using it
in our workflows.
…nd-wheel-with-pip

Install/upgrade setuptools and wheel when upgrading pip
⚠️ CONFLICT! Lineage pull request for: skeleton
…nore_directives

Update the dependabot ignore configuration
…to-roles-block

Prefer ansible.builtin.include_role to a roles block
@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label May 22, 2023
@jmorrowomni jmorrowomni assigned jmorrowomni and unassigned jsf9k and dav3r May 22, 2023
@jmorrowomni jmorrowomni marked this pull request as ready for review May 22, 2023 19:29
.github/dependabot.yml Show resolved Hide resolved
.github/dependabot.yml Show resolved Hide resolved
@jsf9k
Copy link
Member

jsf9k commented May 22, 2023

I would say that this change requires a version bump, since although the code hasn't functionally changed it has changed. What do you say, @mcdonnnj?

.github/dependabot.yml Outdated Show resolved Hide resolved
.github/dependabot.yml Outdated Show resolved Hide resolved
@jsf9k
Copy link
Member

jsf9k commented May 22, 2023

I would say that this change requires a version bump, since although the code hasn't functionally changed it has changed. What do you say, @mcdonnnj?

@jmorrowomni, please see here, which also applies to this PR.

Copy link
Member

@jsf9k jsf9k left a comment

Choose a reason for hiding this comment

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

You need to update nessus.yml to use ansible.builtin.include_role.

@jmorrowomni
Copy link
Contributor

You need to update nessus.yml to use ansible.builtin.include_role.

@jsf9k Code updated in 4836612. Release will be available whenever GitHub decides it likes me enough to let me create one

@jsf9k
Copy link
Member

jsf9k commented May 26, 2023

You need to update nessus.yml to use ansible.builtin.include_role.

@jsf9k Code updated in 4836612. Release will be available whenever GitHub decides it likes me enough to let me create one

Excellent! Now we have an example to send along to GitHub support. I'll do that now.

@jmorrowomni jmorrowomni merged commit 2c41b30 into develop May 31, 2023
6 checks passed
@jmorrowomni jmorrowomni deleted the lineage/skeleton branch May 31, 2023 11:19
@jsf9k
Copy link
Member

jsf9k commented May 31, 2023

@jmorrowomni, after you create a pre-release or release the code in terraform-post-packer must be run for the new AMI to be made available to COOL staging or production, respectively. I took care of it for this repository, but in the future you should make sure to ask someone in @cisagov/team-ois to do this for you for any *-packer repo PRs where a pre-release or release is created.

@jmorrowomni
Copy link
Contributor

@jmorrowomni, after you create a pre-release or release the code in terraform-post-packer must be run for the new AMI to be made available to COOL staging or production, respectively. I took care of it for this repository, but in the future you should make sure to ask someone in @cisagov/team-ois to do this for you for any *-packer repo PRs where a pre-release or release is created.

Understood, will do going forward

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream update This issue or pull request pulls in upstream updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants