Assets uploading

New

Can we able to upload the assets without IP address, I mean we are using same assets for all the instances and for every build and deployment process we need to do the same process like need to run the asset uploading command then once done we need to take asset_map_id and we need to add in <head> script etc etc.

So can we avoid this adding asset_map_id in the script again because we are using jenkins build pipeline to trigger the deployment process and every time we will get new instances in the process so every time manually we need to get the asset_map_id and adding.

Its not a proper way to set every time. Do we have any alternative way to do this?

0

Comments

3 comments

  • Hey @Shilpa! Thanks so much for reaching out! 😊

    I see you’ve been in contact with our support team regarding this question. It looks like this question requires a bit more clarity, and our awesome support team will continue the conversation with you in your current ticket to help provide you with an answer. 

    Please let me know if you have anymore questions!

    0
  • I’m bumping this thread again to hear if there’s been any progress.

    @Shilpa, were you and your team able to find a solution to this?

    We’re struggling with the same problem, as our stylesheets are behind authentication (e.g. not public).

    The fullstory asset uploader executable generates a new id every time its run, so we can’t just have a static id for asset identification, and reupload the assets at will, but must seemingly update the id in the header, every time the executable has been run.

    Thus, after much back and forth with the fullstory support, we don’t seem to have much of an option, but to put asset uploader into our build process, which is a no-go from security point of view. From a Chief Security Officer point of view, a third-party executable being exposed to all source code poses a great security risk.

    0
  • Hey @IFS-Alex ! Thanks for your post.

    We understand the difficulties you’ve faced with FullStory’s asset uploader tool creating new IDs with each run, especially in light of authentication constraints on your stylesheets. Your concerns about security risks in integrating the asset uploader into your build process are duly noted and have been communicated to our team internally. 

    That said, in communications with your team, we informed them that the suggested workflow is, unfortunately, not currently on our roadmap. At present, the recommended methods for ensuring proper playback entail utilizing the FullStoryBot or the existing Asset Uploader tool.

    Let us know if any other questions or concerns come up that we can assist you with.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post