Replace properties in a file from linux shell commands
up vote
0
down vote
favorite
I used below command to update the application.properties file. But it is not working.
REPLACEUN=test
REPLACEPW=test@123
sed -i "s/(spring.datasource.username=).*$/1${REPLACEUN}/" test-
inventory-backendcode/Test Backend/src/main/resources/application.properties
What is wrong with this? When I cd to the directory and run the command, working fine.
this is the error i got.
*
sed: can't read test-inventory-backendcode/Test
Backend/src/main/resources/application.properties: No such file or
directory
*
linux shell
asked Nov 28 at 5:49
Janith
84
|
show 2 more comments
up vote
0
down vote
favorite
I used below command to update the application.properties file. But it is not working.
REPLACEUN=test
REPLACEPW=test@123
sed -i "s/(spring.datasource.username=).*$/1${REPLACEUN}/" test-
inventory-backendcode/Test Backend/src/main/resources/application.properties
What is wrong with this? When I cd to the directory and run the command, working fine.
this is the error i got.
*
sed: can't read test-inventory-backendcode/Test
Backend/src/main/resources/application.properties: No such file or
directory
*
linux shell
asked Nov 28 at 5:49
Janith
84
1
The path you have specified for sed is considered relative to your current directory, so it will fail when the command is run from another location.
– Haxiel
Nov 28 at 6:00
I am running this by staying Test_Backend_Parameterized_Deployment directory. Then after I have test-inventory-backendcode/Test Backend/src/main/resources/application.properties recursively. Then what will be the solution? Test_Backend_Parameterized_Deployment is Jenkins workspace
– Janith
Nov 28 at 6:11
You can either add a cd command to change to the Jenkins workspace directory before the sed command, or you can specify the absolute path to the properties file in the sed command.
– Haxiel
Nov 28 at 6:24
My absolute path is,/var/lib/jenkins/workspace/Test_Backend_Parameterized_Deployment/test-inventory-backendcode/Test Backend/src/main/resourcesI have included it but not worked. Addingcdcommand before executesedworks fine
– Janith
Nov 28 at 6:30
The path in the error message and the path in the command does not match up. There are newlines in different places. If you manually edited these, then edit again to make sure that the error message and the script are correct. Newline is a valid character in a Unix filename.
– Kusalananda
Nov 28 at 6:48
|
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I used below command to update the application.properties file. But it is not working.
REPLACEUN=test
REPLACEPW=test@123
sed -i "s/(spring.datasource.username=).*$/1${REPLACEUN}/" test-
inventory-backendcode/Test Backend/src/main/resources/application.properties
What is wrong with this? When I cd to the directory and run the command, working fine.
this is the error i got.
*
sed: can't read test-inventory-backendcode/Test
Backend/src/main/resources/application.properties: No such file or
directory
*
linux shell
asked Nov 28 at 5:49
Janith
84
I used below command to update the application.properties file. But it is not working.
REPLACEUN=test
REPLACEPW=test@123
sed -i "s/(spring.datasource.username=).*$/1${REPLACEUN}/" test-
inventory-backendcode/Test Backend/src/main/resources/application.properties
What is wrong with this? When I cd to the directory and run the command, working fine.
this is the error i got.
*
sed: can't read test-inventory-backendcode/Test
Backend/src/main/resources/application.properties: No such file or
directory
*
linux shell
linux shell
asked Nov 28 at 5:49
Janith
84
asked Nov 28 at 5:49
Janith
84
asked Nov 28 at 5:49
Janith
84
asked Nov 28 at 5:49
Janith
84
asked Nov 28 at 5:49
Janith
84
84
1
The path you have specified for sed is considered relative to your current directory, so it will fail when the command is run from another location.
– Haxiel
Nov 28 at 6:00
I am running this by staying Test_Backend_Parameterized_Deployment directory. Then after I have test-inventory-backendcode/Test Backend/src/main/resources/application.properties recursively. Then what will be the solution? Test_Backend_Parameterized_Deployment is Jenkins workspace
– Janith
Nov 28 at 6:11
You can either add a cd command to change to the Jenkins workspace directory before the sed command, or you can specify the absolute path to the properties file in the sed command.
– Haxiel
Nov 28 at 6:24
My absolute path is,/var/lib/jenkins/workspace/Test_Backend_Parameterized_Deployment/test-inventory-backendcode/Test Backend/src/main/resourcesI have included it but not worked. Addingcdcommand before executesedworks fine
– Janith
Nov 28 at 6:30
The path in the error message and the path in the command does not match up. There are newlines in different places. If you manually edited these, then edit again to make sure that the error message and the script are correct. Newline is a valid character in a Unix filename.
– Kusalananda
Nov 28 at 6:48
|
show 2 more comments
1
The path you have specified for sed is considered relative to your current directory, so it will fail when the command is run from another location.
– Haxiel
Nov 28 at 6:00
I am running this by staying Test_Backend_Parameterized_Deployment directory. Then after I have test-inventory-backendcode/Test Backend/src/main/resources/application.properties recursively. Then what will be the solution? Test_Backend_Parameterized_Deployment is Jenkins workspace
– Janith
Nov 28 at 6:11
You can either add a cd command to change to the Jenkins workspace directory before the sed command, or you can specify the absolute path to the properties file in the sed command.
– Haxiel
Nov 28 at 6:24
My absolute path is,/var/lib/jenkins/workspace/Test_Backend_Parameterized_Deployment/test-inventory-backendcode/Test Backend/src/main/resourcesI have included it but not worked. Addingcdcommand before executesedworks fine
– Janith
Nov 28 at 6:30
The path in the error message and the path in the command does not match up. There are newlines in different places. If you manually edited these, then edit again to make sure that the error message and the script are correct. Newline is a valid character in a Unix filename.
– Kusalananda
Nov 28 at 6:48
1
1
The path you have specified for sed is considered relative to your current directory, so it will fail when the command is run from another location.
– Haxiel
Nov 28 at 6:00
The path you have specified for sed is considered relative to your current directory, so it will fail when the command is run from another location.
– Haxiel
Nov 28 at 6:00
I am running this by staying Test_Backend_Parameterized_Deployment directory. Then after I have test-inventory-backendcode/Test Backend/src/main/resources/application.properties recursively. Then what will be the solution? Test_Backend_Parameterized_Deployment is Jenkins workspace
– Janith
Nov 28 at 6:11
I am running this by staying Test_Backend_Parameterized_Deployment directory. Then after I have test-inventory-backendcode/Test Backend/src/main/resources/application.properties recursively. Then what will be the solution? Test_Backend_Parameterized_Deployment is Jenkins workspace
– Janith
Nov 28 at 6:11
You can either add a cd command to change to the Jenkins workspace directory before the sed command, or you can specify the absolute path to the properties file in the sed command.
– Haxiel
Nov 28 at 6:24
You can either add a cd command to change to the Jenkins workspace directory before the sed command, or you can specify the absolute path to the properties file in the sed command.
– Haxiel
Nov 28 at 6:24
My absolute path is,
/var/lib/jenkins/workspace/Test_Backend_Parameterized_Deployment/test-inventory-backendcode/Test Backend/src/main/resources I have included it but not worked. Adding cd command before execute sed works fine– Janith
Nov 28 at 6:30
My absolute path is,
/var/lib/jenkins/workspace/Test_Backend_Parameterized_Deployment/test-inventory-backendcode/Test Backend/src/main/resources I have included it but not worked. Adding cd command before execute sed works fine– Janith
Nov 28 at 6:30
The path in the error message and the path in the command does not match up. There are newlines in different places. If you manually edited these, then edit again to make sure that the error message and the script are correct. Newline is a valid character in a Unix filename.
– Kusalananda
Nov 28 at 6:48
The path in the error message and the path in the command does not match up. There are newlines in different places. If you manually edited these, then edit again to make sure that the error message and the script are correct. Newline is a valid character in a Unix filename.
– Kusalananda
Nov 28 at 6:48
|
show 2 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484587%2freplace-properties-in-a-file-from-linux-shell-commands%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The path you have specified for sed is considered relative to your current directory, so it will fail when the command is run from another location.
– Haxiel
Nov 28 at 6:00
I am running this by staying Test_Backend_Parameterized_Deployment directory. Then after I have test-inventory-backendcode/Test Backend/src/main/resources/application.properties recursively. Then what will be the solution? Test_Backend_Parameterized_Deployment is Jenkins workspace
– Janith
Nov 28 at 6:11
You can either add a cd command to change to the Jenkins workspace directory before the sed command, or you can specify the absolute path to the properties file in the sed command.
– Haxiel
Nov 28 at 6:24
My absolute path is,
/var/lib/jenkins/workspace/Test_Backend_Parameterized_Deployment/test-inventory-backendcode/Test Backend/src/main/resourcesI have included it but not worked. Addingcdcommand before executesedworks fine– Janith
Nov 28 at 6:30
The path in the error message and the path in the command does not match up. There are newlines in different places. If you manually edited these, then edit again to make sure that the error message and the script are correct. Newline is a valid character in a Unix filename.
– Kusalananda
Nov 28 at 6:48