Skip to content

war_source can(not) be a local path #576

@bencomp

Description

@bencomp

I'm trying to install a WAR file using a custom resource that wraps tomcat::war.

Describe the Change You Would Like

The @param description for the war_source parameter says:

Valid options: a string containing a puppet://, http(s)://, or ftp:// URL.

However, the README says

The war_source can be a local path or a puppet:///, http://, or ftp:// URL.

I would like these explanations to be the same (and correct, of course), so that I can understand whether a local path as war_source is a valid option. As far as I can tell, the code does not actually require URLs, but I am not sure that I understand it enough to trust my judgment.
Also note the different number of /s in the puppet: URLs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions