Shell script - How to export a script as a string?

Question

I have a large shell script I'm trying to append to bashprofile on VM bootup:

I want this script to get appended to the bashrc file. I've tried the following:

read -d '' load_script << EOF
// code here
EOF

but it starts evaluating the variables automatically, I just want to push this script into the bashrc file. How can I do this?

Script

writer_endpoint=$(aws neptune describe-db-clusters --db-cluster-identifier redacted | jq .DBClusters[0] | jq .Endpoint | tr -d '"')
reader_endpoint=$(aws neptune describe-db-clusters --db-cluster-identifier redacted | jq .DBClusters[0] | jq .ReaderEndpoint| tr -d '"')
writer_endpoint_status=$(awscurl https://$writer_endpoint:8182/status --service neptune-db | jq .status)
reader_endpoint_status=$(awscurl https://$reader_endpoint:8182/status --service neptune-db | jq .status)
cat << EOF

                +==========+===============+
                | Endpoint | Health Status |
                +==========+===============+
                | Reader   | $writer_endpoint_status     |
                +----------+---------------+
                | Writer   | $reader_endpoint_status     |
                +----------+---------------+

********************************************************************************************************
Welcome to the bastion host, used to debug connectivity and queries against the Neptune graph DB.
********************************************************************************************************

[Reader Endpoint]:
$reader_endpoint

[Writer Endpoint]:
$writer_endpoint

[Example - Check status of reader replica]:
awscurl https://$writer_endpoint:8182/status --service neptune-db

*******************************************************************************************************

Seems like you missed a part of your code. There is no closing `EOF`. Anyways, a [literal HereDocument](https://mywiki.wooledge.org/HereDocument) should do the trick. Write `<< 'EOF'` instead of `<< EOF`. — Socowi, May 21 '21 at 20:32
Like if I "source filename.sh" I need to first create the file based on these contents. But I'm having issues with escaping everything, etc. — Ryan, May 21 '21 at 20:38
@Socowi, I can try this. I have two spots where I use << EOF. Which one are you referring to? — Ryan, May 21 '21 at 20:39
Seems like I'm still having the same issue. Can you try showing it via an answer? — Ryan, May 21 '21 at 20:41
It still seems the final EOF (which should be in the string) cannot be escaped. How can I achieve that? — Ryan, May 21 '21 at 20:52
Why do you think it needs to be escaped? Quote only the starting sigil. — Charles Duffy, May 21 '21 at 20:52
If the concern is that you have two different heredocs (f/e, embedding one inside the other), just pick a different sigil instead of using `EOF`. Literally any string will work. For example, you can use `<<'OUTER'` and `<<'INNER'`, terminated by `INNER` and `OUTER`. — Charles Duffy, May 21 '21 at 20:53
I have two EOF in the script. Updated the OP. There is an EOF embedded in the string that needs to be escaped — Ryan, May 21 '21 at 20:53

Shell script - How to export a script as a string?

Script

0 Answers0