Problem: pipelines are not always discoverable

[sevein]

SS stores the remote_name of a pipeline when it's created for consequent API access, e.g. re-ingest.

remote_name = models.CharField(
    max_length=256,
    default=None,
    null=True,
    blank=True,
    help_text="Host or IP address of the pipeline server for making API calls.")

This field is also editable from the web interface.

When a pipeline is created via the SS API, this field is populated after the REMOTE_ADDR header unless the client provides a value via the remote_name property.

The problem is that the dashboard doesn't allow users to provide a custom value so SS always fallbacks to the value found in the REMOTE_ADDR header which is problematic under some circumstances.

[jrwdunham]

Assuming a URL is scheme:[//[user[:password]@]host[:port]][/path][?query][#fragment], are you proposing adding a new attribute to Pipeline so that Pipeline().remote_url must be a valid scheme:[//host[:port]]?

Or are you thinking of modifying the logic around Pipeline().remote_name so we can accept both scheme-less and schemed URLs?

[sevein]

Or are you thinking of modifying the logic around Pipeline().remote_name so we can accept both scheme-less and schemed URLs?

I didn't think much about it but I like the way ^ sounds. It would mean that we can solve the problem without a database migration - is that ok?

[jrwdunham]

Sounds good to me.

[sevein]

I think that this issue needs to remain open until SS learns a new parameter that allows the user to indicate the URI of the pipeline in the create pipeline endpoint. This parameter should be provided by Archivematica when it performs the self-registration process.

[sevein]

@sromkey, I think that we can close this issue.

SS v0.11 included #267 which made the following changes:

• Parse Pipeline.remote_name as URLs (797d6a9).
• Create pipeline endpoint to honour remote_name(134e33b)
• Add SS_INSECURE_SKIP_VERIFY env so TLS cert verification can be disabled when the scheme found in the URI is https (ecacbec7d066f072966fc15342417b3ac381b929)

I think that these changes together already enabled the dashboard to provide a URI as the remote name. The remaining changes (provide a URI) need to happen in the AM repo.