Upcoming file migration for workflow automation



  • Joel Ordesky (Private Guru)

    Question to the above:

    I was told in relation to public url for images hosted in Podio the following:

    If you use the "Image (Public URL)" field token to store Podio image files publicly, AND use the HTTPS URL manually, then:

    You need to replace or update all instances of "https://227e3ae233b1be7b91ea-c92c8b85a97b470d1d820c3563880a61.ssl.cf5.rackcdn.com" with "https://pfuserfiles.globiflow.com" in your use case.

    However this not quite how it works for me. 

    I have an image stored on a Podio item. I get Globiflow to give me the Public URL. I get a URL that is:

    Will this URL which is http: redirect to the https: so I do not need to change all of my hard coded flows that use this existing URL.  Does the age of the originally hosted file and or the age of the Public URL matter as long as the URL is through pfuserfiles.globiflow.com as opposed to directly through the rackcdn.com url. 

    Comment actions Permalink
  • Pallabi Patnaik

    Hi Joel Ordesky (Private Guru)

    - The age of the file matters as long as the file is directly uploaded on GF. If the file is more than a year old, then it should be re-uploaded.

    - But if the file was originally uploaded to Podio and GF is just consuming the file which currently still exists in Podio, then no action is needed.

    Hope this answers your query.

    Comment actions Permalink
  • Joel Ordesky

    Not sure if this really gets to the heart of the question. Clearly, things with URL that reference the rackcdn.com are a problem.

    It also seems likely that http://pfuserfiles.globiflow.com will redirect to https://pfuserfiles.globiflow.com however the whole issue of things uploaded to Globiflow that are over a year old vs Podio Items consumed by Globiflow does not seem to address items that are in Podio but were moved onto the CDN for consumption by a Public URL for images.

    I think the unanswered question is does an existing previously created public URL simply consume an image off Podio or does the public URL request, push content to a CDN and if so it would seem that the age of the pushed file might be an issue, however, it would very hard to know the age of such public URL and resulting files and replacing them might not be as easy if the public URL is being used as described above as a hardcoded link. 

    I am guessing if a Flow calls for the public URL or uses the Podio image link that the file is pushed to the CDN each time the flow is used so in that method of use this migration would not be an issue. Again, it is the possible issue of items in Podio for which there is a public URL that was created over a year ago and therefore I am wondering if that created a file.

    My own research implies it is highly likely that the old links created referencing files that are on Podio are not really referencing them but are referencing files that were pushed to the CDN when the URL was created. It seems that each time a public URL is created or referenced via a flow that the image file from Podio is re-pushed to the CDN (not the most storage efficient model) and if that is the case the notification should be amended to clarify that Public URL's for images that were generated over a year ago and are still in use due to a hardcoded use of that link need to be refreshed prior to the date in May and replaced in their code. 

    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk