Closed noelmcloughlin closed 3 years ago
Best reviewed: commit by commit
Powered by Pull Assistant. Last update 3759b66 ... cabc79f. Read the comment docs.
Added support for Archlinux (CI/CD) with HTTPS/SSL and modules.
I discussed this PR with @myii and because it's too big to review I'll selfie-merge on the following basis:
Pillar data is unchanged. The primary change is state-names were refactored as part of the alignment with template-formula.
:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
@noelmcloughlin Nice work, the breaking changes listed in the changelog make things so much easier to follow -- appreciate it.
Just a little note for posterity.
I wasn't able to git pull
these changes without manual operation (but I do use my formulas' repos in non-standard ways to most people). I was getting this error:
error: Updating the following directories would lose untracked files in them:
apache/vhosts
Was able to check the problem using git clean
in dry-run mode:
$ git clean -xdfn
...
Would remove apache/vhosts/.cleanup.sls.un~
Would remove apache/vhosts/.minimal.tmpl.un~
Would remove apache/vhosts/.proxy.tmpl.un~
Would remove apache/vhosts/.redirect.tmpl.un~
Would remove apache/vhosts/.standard.tmpl.un~
...
So the main point is that making modifications to the directory structure could lead to issues with certain files being present in the directories that are being moved (i.e. those covered by .gitignore
).
This is more so a point of awareness, there's not much we could do about this.
Standardised this implementation with 7dc0ece4f5d1659be266f82f3dfe05a82833f41c.
@noelmcloughlin It looks like you're using an older version of libtofs.jinja
when preparing these PRs. The new version has been pushed to pretty much all formulas that are using TOFS.
BREAKING CHANGE: Module .sls files are moved to /config/modules/ subdirectory. template-formula alignment may introduce a breaking change. See README for states.
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?YES
Related issues and/or pull requests
Includes #225 and #259 Fixes #79, #238, #258, #262, #265, #266
Describe the changes you're proposing
While using this formula I saw various issues and inconsistencies.
This PR is an attempt to improve formula quality while keeping the same functionality.
I'm sorry the PR is so big but there is no easy way to improve feature/test coverage without restructuring. The CI/CD is passing for all platforms except:
Further work is required to address remaining open issues.
There may be better ways of processing modules but this PR relies on the existing solutions.
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context