Open bramd opened 4 years ago
Best reviewed: commit by commit
Powered by Pull Assistant. Last update 70ea2e2 ... 70ea2e2. Read the comment docs.
Thanks for this PR, @bramd -- hopefully @sticky-note will get a chance to review this soon. Generally looks fine (other than the fact the map.jinja
is already way too unwieldy). We should really use our latest 20.04
image here as well to test these changes; I'll try to do that in the near future.
I had problems with this too. The commit looks good to me, although there might be better solutions for map.jinja. However, can this pull-request still be accepted?
I had problems with this too. The commit looks good to me, although there might be better solutions for map.jinja. However, can this pull-request still be accepted?
@crosscodr Can you confirm that these changes work for you?
Almost, but a few packages are not available in the official ubuntu-sources:
I searched for the dependency-packages (php-
I also noticed, that this part
'SQL': { 'sql.safe_mode': 'Off' },
can be omitted, hence it is removed since php7.2 (https://www.php.net/manual/de/ini.core.php#ini.sql.safe-mode).
This are my findings so far. There may be other things to optimise, but these are the main problems I can see.
Thanks @crosscodr. @bramd can you use the last comment to update this PR?
Or maybe we should review and enhance #214.
@Myii How can I pull this branch to make some rebase aand fixes before merging. I don't have right to write on @bramd repo
@myii How can I pull this branch to make some rebase aand fixes before merging. I don't have right to write on @bramd repo
Apologies for the delay, @sticky-note -- the CI situation is still taking up a lot of my attention.
There are a number of ways to approach this but I don't want to write a whole essay here! The easiest suggestion is to simply open up another PR, using the same commit again (with your amendments). That way, the authoring credit still goes back to the original author.
Rebasing would be good because I just upgraded the CI matrix here to include the latest platforms including ubuntu-20.04
:
Any changes you make will have to be reflected in the relevant map.jinja
verification files here:
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
?No.
Related issues and/or pull requests
Describe the changes you're proposing
The formula did not work out of the box on a fresh Ubuntu 20.04 system. Some PHP 7.2 paths and package names were hardcoded, where Ubuntu 20.04 repositories contain PHP 7.4.
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