Hi All,

Though i do understand how to use sed command and it's very easy but i am stuck in a situation where i need to change one value but it's changing all value.

Below i have component name with their version. Suppose if i want to change the component2 version says v2, then component5, component7 get also affected.
gauravrishi@administrator-ThinkPad-L470:/tmp$ cat 1.txt
component1: "v44"
component2: "v1"
component3: "v17"
component4: "v664"
component5: "v152"
component6: "v220"
component7: "v100"
component8: "v434"

sed -i "s/v1/v14/" 1.txt


component1: "v44"
component1: "v14"
component3: "v147"
component4: "v664"
component5: "v1451"
component6: "v1410"
component7: "v1400"
component8: "v434"

The value get change. I only want to change the value which i have mentioned in sed command.

there are several ways, probably:

1 members found this post helpful.

The more you use sed (and regex) the more you will see the fallacy of this statement.

2 members found this post helpful.

Hi Thanks for your comment but the thing which i am looking it's not working.

new_version=14

current_version=$(cat 1.txt |grep component1 | cut -d: -f2 | sed 's/"//g' | sed 's/^..//' | tail -n1)

if [ "$current_version" == "$new_version" ]
then
echo "Version already present"
exit 1
else
echo "Changing the version"
sed -i "s/${current_version}/${new_version}/g" 1.txt
echo "current version: $current_version ----> new version: $new_version"

fi

Can you please help why the values are getting change. This is the code which i am using,

Thanks it's working for me. I have found the answer for this by using below mentioned command.

sed 's/"'${current_version}'"/"'${new_version}'"/' buildVersion.yaml

That is great!
(if you really want to say thanks just click on yes)

1 members found this post helpful.

You need to understand the effect of single versus double quotes - and the effect on the shell.
I prefer to use double quotes to allow natural variable substitution, and escape embedded double quotes (preferably avoid them altogether) - like thisI find consecutive quotes get confusing.

Thanks for your suggestions.

Could you please confirm what if I am using double quotes the code which I am using. Will this createa problem

current_version=$(cat 1.txt |grep component1 | cut -d: -f2 | sed 's/"//g' | sed 's/^..//' | tail -n1)

Maybe could be shortened:

Normally the sed code should be in 'ticks'; your code correctly has the shell variable outside so the shell can substitute them.
But they must not contain special characters. If you want to allow special characters the variables must be in "quotes" for the shell to only substitute but not further expand them:
For demonstration I put these quotes in red - in reality the chain "'" looks a bit confusing.
Therefore, in this case, putting the sed code in "quotes" is a good alternative.

sed -r 's/(component2:\s*"v)\w+/\12/' 1.txt