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

Handle duplicate file declaration for foreman::app_root #969

Merged
merged 2 commits into from
Jul 22, 2021
Merged

Handle duplicate file declaration for foreman::app_root #969

merged 2 commits into from
Jul 22, 2021

Conversation

chr1s692
Copy link
Contributor

@chr1s692 chr1s692 commented Jul 8, 2021

Currently we're using your modul to install and configure Foreman.
We want to install Foreman in its own filesystem, but the file ressource for $foreman::app_root makes it hard to implement this in puppet - it will always result in duplicate ressource. Furthermore i'm not sure, if this ressource is necessary or placed in the right class (ordering, first install the package and then create the directory?!).

Testing if this directory is already defined gives other the chance to do some stuff, e.g. creating a filesystem before installing foreman :)

Currently we're using your modul to install and configure Foreman. 
We want to install Foreman in its own filesystem, but the file ressource for $foreman::app_root makes it hard to implement this in puppet - it will always result in duplicate ressource.  Furthermore i'm not sure, if this ressource is necessary or placed in the right class (ordering, first install the package and then create the directory?!).

Testing if this directory is already defined gives other the chance to do some stuff, e.g. creating a filesystem before installing foreman :)
Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

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

Furthermore i'm not sure, if this ressource is necessary or placed in the right class (ordering, first install the package and then create the directory?!).

Normally the package install creates the directory. So the whole definition may not be needed. So I wonder why you want to manage this in a different way.

manifests/config.pp Outdated Show resolved Hide resolved
Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

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

I'm still wondering why you do need to manage it, but I don't mind this.

@ekohl ekohl changed the title file foreman::app_root optional Handle duplicate file declaration for foreman::app_root Jul 22, 2021
@ekohl ekohl merged commit 85514df into theforeman:master Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants